FHIR © HL7.org  |  Server Home  |  FHIR Server FHIR Server 3.4.11  |  FHIR Version n/a  User: [n/a]

Resource Requirements/FHIR Server from package hl7.fhir.uv.cmhaffr2#current (63 ms)

Package hl7.fhir.uv.cmhaffr2
Type Requirements
Id Id
FHIR Version R5
Source http://hl7.org/fhir/uv/cmhaffr2/https://build.fhir.org/ig/HL7/cmhaff-ig/Requirements-CMHAFFR2-PDS.3.html
Url http://hl7.org/fhir/uv/cmhaffr2/Requirements/CMHAFFR2-PDS.3
Version 2.0.1
Status active
Date 2025-01-30T10:38:20+00:00
Name PDS_3_Usability_and_Accessibility_Assessment
Title PDS.3 Usability and Accessibility Assessment (Header)
Experimental False
Realm uv
Authority hl7

Resources that use this resource

No resources found


Resources that this resource uses

No resources found



Narrative

Note: links and images are rebased to the (stated) source

Generated Narrative: Requirements CMHAFFR2-PDS.3

PDS.3#01SHALL

The App SHALL be assessed against an industry-validated usability assessment tool, using subjects who are demographically-similar to intended users (target audience). For example, user types may include those with motor disabilities, visual impairment, auditory disabilities, etc. [1]

PDS.3#02SHALL

[Intended users include those with motor disabilities] Assess product for usability by people with motor disabilities.[1]

PDS.3#03SHALL

[Intended users include those with visual disabilities] Assess product for usability by visually-impaired and/or color-blind people using a standard mobile screen reader.

PDS.3#04SHALL

[Intended users include those with auditory disabilities] Assess product for usability by people with auditory disabilities.

PDS.3#05SHOULD

Assess product for usability by a sample of intended users. If geared towards a certain age segment or to people with a specific chronic health condition, or to persons with disabilities other than those specified above, usability testing subjects are drawn from these populations.

PDS.3#06SHOULD

Create a written usability assessment plan, including known problems with product usability and mitigation plan. NOTE: for U.S. Realm when an app is sponsored by a HIPAA entity, the force of this criteria is elevated to “SHALL” with plan specifically addressing usability issues for people with visual and motor disabilities.

PDS.3#07SHOULD

Follow design/style guide standards established by the platform provider(s) for the app (e.g., Android, iOS).

PDS.3#08SHOULD

Avoid excessive data use by the app, minimizing it as much as possible warning users when high data usage occurs (e.g., downloads and updates).[2]

PDS.3#09SHOULD

Describe the use cases (business scenarios) and intended users for the app’s main functions.[3]

PDS.3#10SHOULD

Permit flexibility (adaptation) to the user’s specific abilities, needs, or requirements.

PDS.3#11SHOULD

Provide information about accessibility characteristics in the app description and in contextual assistance sections of the app.


Source

{
  "resourceType" : "Requirements",
  "id" : "CMHAFFR2-PDS.3",
  "meta" : {
    "profile" : [
      "http://hl7.org/fhir/uv/cmhaffr2/StructureDefinition/FMHeader"
    ]
  },
  "text" : {
    "status" : "generated",
    "div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\"><p class=\"res-header-id\"><b>Generated Narrative: Requirements CMHAFFR2-PDS.3</b></p><a name=\"CMHAFFR2-PDS.3\"> </a><a name=\"hcCMHAFFR2-PDS.3\"> </a><a name=\"CMHAFFR2-PDS.3-en-US\"> </a><table class=\"grid\"><tr><td><b><a name=\"CMHAFFR2-PDS.3-01\"> </a></b>PDS.3#01</td><td><a href=\"http://hl7.org/fhir/R5/codesystem-conformance-expectation.html#conformance-expectation-SHALL\">SHALL</a></td><td><div><p>The App SHALL be assessed against an industry-validated usability assessment tool, using subjects who are demographically-similar to intended users (target audience). For example, user types may include those with motor disabilities, visual impairment, auditory disabilities, etc. [1]</p>\n</div></td></tr><tr><td><b><a name=\"CMHAFFR2-PDS.3-02\"> </a></b>PDS.3#02</td><td><a href=\"http://hl7.org/fhir/R5/codesystem-conformance-expectation.html#conformance-expectation-SHALL\">SHALL</a></td><td><div><p>[Intended users include those with motor disabilities] Assess product for usability by people with motor disabilities.[1]</p>\n</div></td></tr><tr><td><b><a name=\"CMHAFFR2-PDS.3-03\"> </a></b>PDS.3#03</td><td><a href=\"http://hl7.org/fhir/R5/codesystem-conformance-expectation.html#conformance-expectation-SHALL\">SHALL</a></td><td><div><p>[Intended users include those with visual disabilities] Assess product for usability by visually-impaired and/or color-blind people using a standard mobile screen reader.</p>\n</div></td></tr><tr><td><b><a name=\"CMHAFFR2-PDS.3-04\"> </a></b>PDS.3#04</td><td><a href=\"http://hl7.org/fhir/R5/codesystem-conformance-expectation.html#conformance-expectation-SHALL\">SHALL</a></td><td><div><p>[Intended users include those with auditory disabilities] Assess product for usability by people with auditory disabilities.</p>\n</div></td></tr><tr><td><b><a name=\"CMHAFFR2-PDS.3-05\"> </a></b>PDS.3#05</td><td><a href=\"http://hl7.org/fhir/R5/codesystem-conformance-expectation.html#conformance-expectation-SHOULD\">SHOULD</a></td><td><div><p>Assess product for usability by a sample of intended users. If geared towards a certain age segment or to people with a specific chronic health condition, or to persons with disabilities other than those specified above, usability testing subjects are drawn from these populations.</p>\n</div></td></tr><tr><td><b><a name=\"CMHAFFR2-PDS.3-06\"> </a></b>PDS.3#06</td><td><a href=\"http://hl7.org/fhir/R5/codesystem-conformance-expectation.html#conformance-expectation-SHOULD\">SHOULD</a></td><td><div><p>Create a written usability assessment plan, including known problems with product usability and mitigation plan. NOTE: for U.S. Realm when an app is sponsored by a HIPAA entity, the force of this criteria is elevated to “SHALL” with plan specifically addressing usability issues for people with visual and motor disabilities.</p>\n</div></td></tr><tr><td><b><a name=\"CMHAFFR2-PDS.3-07\"> </a></b>PDS.3#07</td><td><a href=\"http://hl7.org/fhir/R5/codesystem-conformance-expectation.html#conformance-expectation-SHOULD\">SHOULD</a></td><td><div><p>Follow design/style guide standards established by the platform provider(s) for the app (e.g., Android, iOS).</p>\n</div></td></tr><tr><td><b><a name=\"CMHAFFR2-PDS.3-08\"> </a></b>PDS.3#08</td><td><a href=\"http://hl7.org/fhir/R5/codesystem-conformance-expectation.html#conformance-expectation-SHOULD\">SHOULD</a></td><td><div><p>Avoid excessive data use by the app, minimizing it as much as possible warning users when high data usage occurs (e.g., downloads and updates).[2]</p>\n</div></td></tr><tr><td><b><a name=\"CMHAFFR2-PDS.3-09\"> </a></b>PDS.3#09</td><td><a href=\"http://hl7.org/fhir/R5/codesystem-conformance-expectation.html#conformance-expectation-SHOULD\">SHOULD</a></td><td><div><p>Describe the use cases (business scenarios) and intended users for the app’s main functions.[3]</p>\n</div></td></tr><tr><td><b><a name=\"CMHAFFR2-PDS.3-10\"> </a></b>PDS.3#10</td><td><a href=\"http://hl7.org/fhir/R5/codesystem-conformance-expectation.html#conformance-expectation-SHOULD\">SHOULD</a></td><td><div><p>Permit flexibility (adaptation) to the user’s specific abilities, needs, or requirements.</p>\n</div></td></tr><tr><td><b><a name=\"CMHAFFR2-PDS.3-11\"> </a></b>PDS.3#11</td><td><a href=\"http://hl7.org/fhir/R5/codesystem-conformance-expectation.html#conformance-expectation-SHOULD\">SHOULD</a></td><td><div><p>Provide information about accessibility characteristics in the app description and in contextual assistance sections of the app.</p>\n</div></td></tr></table></div>"
  },
  "url" : "http://hl7.org/fhir/uv/cmhaffr2/Requirements/CMHAFFR2-PDS.3",
  "version" : "2.0.1",
  "name" : "PDS_3_Usability_and_Accessibility_Assessment",
  "title" : "PDS.3 Usability and Accessibility Assessment (Header)",
  "status" : "active",
  "date" : "2025-01-30T10:38:20+00:00",
  "publisher" : "HL7 International / Mobile Health",
  "contact" : [
    {
      "telecom" : [
        {
          "system" : "url",
          "value" : "http://www.hl7.org/Special/committees/mobile"
        }
      ]
    }
  ],
  "jurisdiction" : [
    {
      "coding" : [
        {
          "system" : "http://unstats.un.org/unsd/methods/m49/m49.htm",
          "code" : "001",
          "display" : "World"
        }
      ]
    }
  ],
  "statement" : [
    {
      "extension" : [
        {
          "url" : "http://hl7.org/fhir/uv/cmhaffr2/StructureDefinition/requirements-dependent",
          "valueBoolean" : false
        }
      ],
      "key" : "CMHAFFR2-PDS.3-01",
      "label" : "PDS.3#01",
      "conformance" : [
        "SHALL"
      ],
      "conditionality" : false,
      "requirement" : "The App SHALL be assessed against an industry-validated usability assessment tool, using subjects who are demographically-similar to intended users (target audience). For example, user types may include those with motor disabilities, visual impairment, auditory disabilities, etc. [1]"
    },
    {
      "extension" : [
        {
          "url" : "http://hl7.org/fhir/uv/cmhaffr2/StructureDefinition/requirements-dependent",
          "valueBoolean" : false
        }
      ],
      "key" : "CMHAFFR2-PDS.3-02",
      "label" : "PDS.3#02",
      "conformance" : [
        "SHALL"
      ],
      "conditionality" : false,
      "requirement" : "[Intended users include those with motor disabilities] Assess product for usability by people with motor disabilities.[1]"
    },
    {
      "extension" : [
        {
          "url" : "http://hl7.org/fhir/uv/cmhaffr2/StructureDefinition/requirements-dependent",
          "valueBoolean" : false
        }
      ],
      "key" : "CMHAFFR2-PDS.3-03",
      "label" : "PDS.3#03",
      "conformance" : [
        "SHALL"
      ],
      "conditionality" : false,
      "requirement" : "[Intended users include those with visual disabilities] Assess product for usability by visually-impaired and/or color-blind people using a standard mobile screen reader."
    },
    {
      "extension" : [
        {
          "url" : "http://hl7.org/fhir/uv/cmhaffr2/StructureDefinition/requirements-dependent",
          "valueBoolean" : false
        }
      ],
      "key" : "CMHAFFR2-PDS.3-04",
      "label" : "PDS.3#04",
      "conformance" : [
        "SHALL"
      ],
      "conditionality" : false,
      "requirement" : "[Intended users include those with auditory disabilities] Assess product for usability by people with auditory disabilities."
    },
    {
      "extension" : [
        {
          "url" : "http://hl7.org/fhir/uv/cmhaffr2/StructureDefinition/requirements-dependent",
          "valueBoolean" : false
        }
      ],
      "key" : "CMHAFFR2-PDS.3-05",
      "label" : "PDS.3#05",
      "conformance" : [
        "SHOULD"
      ],
      "conditionality" : false,
      "requirement" : "Assess product for usability by a sample of intended users. If geared towards a certain age segment or to people with a specific chronic health condition, or to persons with disabilities other than those specified above, usability testing subjects are drawn from these populations."
    },
    {
      "extension" : [
        {
          "url" : "http://hl7.org/fhir/uv/cmhaffr2/StructureDefinition/requirements-dependent",
          "valueBoolean" : false
        }
      ],
      "key" : "CMHAFFR2-PDS.3-06",
      "label" : "PDS.3#06",
      "conformance" : [
        "SHOULD"
      ],
      "conditionality" : false,
      "requirement" : "Create a written usability assessment plan, including known problems with product usability and mitigation plan. NOTE: for U.S. Realm when an app is sponsored by a HIPAA entity, the force of this criteria is elevated to “SHALL” with plan specifically addressing usability issues for people with visual and motor disabilities."
    },
    {
      "extension" : [
        {
          "url" : "http://hl7.org/fhir/uv/cmhaffr2/StructureDefinition/requirements-dependent",
          "valueBoolean" : false
        }
      ],
      "key" : "CMHAFFR2-PDS.3-07",
      "label" : "PDS.3#07",
      "conformance" : [
        "SHOULD"
      ],
      "conditionality" : false,
      "requirement" : "Follow design/style guide standards established by the platform provider(s) for the app (e.g., Android, iOS)."
    },
    {
      "extension" : [
        {
          "url" : "http://hl7.org/fhir/uv/cmhaffr2/StructureDefinition/requirements-dependent",
          "valueBoolean" : false
        }
      ],
      "key" : "CMHAFFR2-PDS.3-08",
      "label" : "PDS.3#08",
      "conformance" : [
        "SHOULD"
      ],
      "conditionality" : false,
      "requirement" : "Avoid excessive data use by the app, minimizing it as much as possible warning users when high data usage occurs (e.g., downloads and updates).[2]"
    },
    {
      "extension" : [
        {
          "url" : "http://hl7.org/fhir/uv/cmhaffr2/StructureDefinition/requirements-dependent",
          "valueBoolean" : false
        }
      ],
      "key" : "CMHAFFR2-PDS.3-09",
      "label" : "PDS.3#09",
      "conformance" : [
        "SHOULD"
      ],
      "conditionality" : false,
      "requirement" : "Describe the use cases (business scenarios) and intended users for the app’s main functions.[3]"
    },
    {
      "extension" : [
        {
          "url" : "http://hl7.org/fhir/uv/cmhaffr2/StructureDefinition/requirements-dependent",
          "valueBoolean" : false
        }
      ],
      "key" : "CMHAFFR2-PDS.3-10",
      "label" : "PDS.3#10",
      "conformance" : [
        "SHOULD"
      ],
      "conditionality" : false,
      "requirement" : "Permit flexibility (adaptation) to the user’s specific abilities, needs, or requirements."
    },
    {
      "extension" : [
        {
          "url" : "http://hl7.org/fhir/uv/cmhaffr2/StructureDefinition/requirements-dependent",
          "valueBoolean" : false
        }
      ],
      "key" : "CMHAFFR2-PDS.3-11",
      "label" : "PDS.3#11",
      "conformance" : [
        "SHOULD"
      ],
      "conditionality" : false,
      "requirement" : "Provide information about accessibility characteristics in the app description and in contextual assistance sections of the app."
    }
  ]
}

XIG built as of ??metadata-date??. Found ??metadata-resources?? resources in ??metadata-packages?? packages.